Release 10.1A: OpenEdge Data Management:
Database Administration

PROUTIL LOAD qualifier

Performs a binary load of database contents.

Syntax

proutil db-name -C load { filename | -dumplist dumpfile }        build indexes [-TB blocksize] [-TM n]        [[-T dir-name] | [-SS sort-file-directory-specification]]

Parameters

db-name

Specifies the database where you want to load the data. You must completely define the path.

filename

Specifies a single binary dump file that you want to load. You must completely define the path.

-dumplist dumpfile

Specifies a file containing a list of fully qualified binary dump files to load. Use the file created by PROUTIL DUMP, or create one. For more information on dump files, see the "Loading table contents in binary format with PROUTIL" section.

build indexes

Indicates that PROUITL LOAD will simultaneously build the indexes and perform the load.

-TB blocksize

Specifies that the index rebuild will be performed using Speed Sort. blocksize indicates the allocated block size, in kilobytes.

-TM n

Specifies the merge number. n indicates the number of blocks or streams to be merged during the sort process.

-T dir-name

Specifies the name of the directory in which the temporary files are stored. If you do not use this parameter, PROUTIL places temporary files in the current working directory.

-SS sort-file-directory-specification

Identifies the location of a multi-volume sort file specification. If you use the Sort Directory Specification (-SS) parameter, PROUTIL does not use the Temporary Directory (-T) parameter.

Notes

See Chapter 15, "Dumping and Loading," for more information about the LOAD qualifier.
The PROUTIL DUMP and LOAD utilities use cyclic redundancy check (CRC) values to establish the criteria for loading.

The OpenEdge database provides a flexible storage architecture and the ability to relocate objects, such as tables and indexes, while the database remains online. As a result, when you perform a binary load operation, the table numbers in a binary dump file might not match the table numbers in the target database. Therefore, when you perform a binary load operation, the criteria for loading tables is based solely on cyclic redundancy check (CRC) values, and not table numbers.

For example, when you dump a table, the PROUTIL utility calculates a CRC value for the table and stores it in the header of the binary dump file. When you load the table, PROUTIL matches the CRC value stored in the header with the CRC value of the target table. The values must match or the load is rejected.

You can load binary dump files created with a previous version of the PROUTIL DUMP utility, because the current version of PROUTIL LOAD uses the CRC value established when the file was originally dumped. Consequently, the OpenEdge database maintains backwards compatibility.

However, you cannot use PROUTIL LOAD from Version 8.3 or earlier to load a binary dump file created using the Version 9.0 or later of the PROUTIL DUMP utility. The earlier versions of PROUTIL DUMP and LOAD did not use CRC values to establish the criteria for loading, but instead used other mechanisms, such as:

Looking up table RecIDs in a target database using the table number stored in the header of the binary dump file.
Matching table numbers in the header of the binary dump file with table numbers in a target database.
Comparing the number of fields in the binary dump file with the number of fields in the target database.
PROUTIL LOAD supports loading binary large objects (BLOBS).
When using PROUTIL LOAD with the Build Indexes option, PROUTIL marks the existing indexes as inactive. Once PROUTIL successfully creates the indexes, it marks the indexes active. This means that if the binary load is aborted for any reason, PROUTIL leaves the table with no active indexes.
Tables loaded with the build indexes option must be empty.